ABSTRACT
Seamless tracing of the requirements and associating them with the models and the simulation results is becoming increasingly important. This can be used to support several activities such as variant handling, impact analysis, component reuse, verification, and validation. This work in progress paper presents an approach for combining traceability with requirement verification in Modelica. Traceability is supported via the OSLC specification standard combined with Git version control system. All operations on artifacts of interest are traced. Currently, the traceability data is stored in a graph database which can be queried for generating various reports such as impact analysis, variant handling, etc.
- Lena Buffoni and Peter Fritzson. 2014. Expressing Requirements in Modelica. (2014).Google Scholar
- Alfredo Garro, Andrea Tundis, Daniel Bouskela, Audrey Jardin, Nguyen Thuy, Martin Otter, Lena Buffoni, Peter Fritzson, Martin SjÃűlund, Wladimir Schamai, and Hans Olsson. 2016. On formal cyber physical system properties modeling: A new temporal logic language and a Modelica-based solution. In 2016 IEEE International Symposium on Systems Engineering (ISSE). 1--8.Google ScholarCross Ref
- Alachew Mengist, Adrian Pop, Adeel Asghar, and Peter Fritzson. 2017. Traceability Support in OpenModelica Using Open Services for Lifecycle Collaboration (OSLC). In Proceedings of the 12th International Modelica Conference. Modelica Association and Linköping University Electronic Press.Google ScholarCross Ref
- Martin Otter, Nguyen Thuy, Daniel Bouskela, Lena Buffoni, Hilding Elmqvist, Peter Fritzson, Alfredo Garro, Audrey Jardin, Hans Olsson, Maxime Payelleville, Wladimir Schamai, Eric Thomas, and Andrea Tundis. 2015. Formal Requirements Modeling for Simulation-Based Verification. (2015).Google Scholar
- Wladimir Schamai. 2013. Model-Based Verification of Dynamic System Behavior against Requirements.Google Scholar
- Wladimir Schamai, Lena Buffoni, Nicolas Albarello, Pablo Fontes De Miranda, and Peter Fritzson. 2015. An Aeronautic Case Study for Requirement Formalization and Automated Model Composition in Modelica. (2015).Google Scholar
Index Terms
- Traceability and impact analysis in requirement verification
Recommendations
Traceability and model checking to support safety requirement verification
FSE 2014: Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software EngineeringEnsuring safety-critical software safety requires strict verification of the conformance between safety requirements and programs. Formal verification techniques, such as model checking and theorem proving, can be used to partially realize this ...
Toward improved traceability of non-functional requirements
TEFSE '05: Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineeringThis position paper examines current practices and challenges for tracing non-functional requirements (NFRs). Anecdotal evidence suggests that many organizations do not effectively trace NFRs and that functional changes are often implemented with very ...
Utilizing use case classes for requirement and traceability modeling
MS'06: Proceedings of the 17th IASTED international conference on Modelling and simulationChanges to the UML 2.0 revision indicate that clarifications on the future of traditional use case needs to take place. The indications are that the use case notation can be replaced by use-case classes. Use case classes model requirement types as ...
Comments